SEO: focus key finder on key intent, widen BPM detector mic cluster - #54
Merged
Merged
Conversation
…ster GSC query data showed the two tool pages were competing for the same BPM terms. /tools/key-analyzer lost its BPM queries to /tools/bpm-detector and slid from position 48.6 to 57.3 with zero clicks from any named query; 112 of its 127 named queries now sit past position 50. Key finder — commit the page to key intent: - retitle to "Song Key Finder - Detect the Key of Any MP3, No Upload" - drop BPM from the H1, description and social metadata - cut the meta keywords array from 17 sprawling terms to 5 key-intent ones - promote the no-upload/private angle from the fifth H3 to the first H2 - add "MP3 Key Finder" and "Song Key Detector" H2s matching its own highest-impression queries - point tempo intent out to the BPM detector and tap tempo tools BPM detector — build on the cluster that already ranks 5-10: - H1 now carries the microphone framing the title already used - add four live-audio sections (speaker, phone mic, vinyl/radio/DJ set, live band) targeting queries adjacent to the ones ranking top 10 - link in from the beatmatching and tap tempo guides with mic anchor text Also removes a duplicate BreadcrumbList schema on the key finder page: Breadcrumbs already emits its own, so the manual generateBreadcrumbSchema block was a second competing copy. The visible trail was a lone "Key Finder" crumb while the schema declared Home > Tools > Key Finder; both now agree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
GSC query-level data showed the two tool pages were competing for the same BPM terms, and the key finder was losing:
/tools/key-analyzer/tools/bpm-detectorThe key finder's prior top queries were BPM ones (
bpm checker16 imp,bpm analyzer12). Those moved to the detector page over exactly the window the analyzer fell — Google reassigned BPM intent, and the analyzer lost that signal without consolidating anything on "key" to replace it. Its impressions doubled purely by being shown for more bad queries: 112 of 127 named queries now sit past position 50, with zero in the top 20.Meanwhile the detector has a genuine top-10 cluster it can build on —
bpm finder microphone5.4,bpm mic7.3,bpm microphone9.0,bpm counter microphone9.5 — while its head terms (bpm detector59.0,tempo detector59.2) are a page-6 fight not worth picking.Changes
Key finder — commit to key intent
Song Key Finder - Detect the Key of Any MP3, No UploadMP3 Key FinderandSong Key DetectorH2s matching its own highest-impression queries (key detector27 imp,key finder mp3pos 45.6,mp3 key finderpos 44.7)BPM detector — widen the cluster that already ranks
<title>already used (was a bareBPM Detector, competing on the term it ranks 59th for)Bug fix
/tools/key-analyzerwas injecting two competingBreadcrumbListschemas —<Breadcrumbs>already emits its own, so the manualgenerateBreadcrumbSchemablock was a duplicate. The visible trail was also a loneKey Findercrumb while the schema declaredHome > Tools > Key Finder. Both now agree, matching the detector page's pattern.Verification
pnpm buildpasses; both pages prerender staticapplication/ld+jsonBreadcrumbList script tag per page (the second raw-string occurrence is Next's RSC flight payload, not a parsed script tag)<title>, and H2 structure in the built HTMLpnpm linthas 4 errors, all pre-existing onmainin files this PR doesn't touch (cookie-consent.tsx,ad-slot.tsx,analytics.tsx)Note
Copy/metadata changes only — no logic touched. Effects take weeks to show in GSC; worth re-running
scripts/fetch-analytics.mjsin ~3-4 weeks to check whether the analyzer consolidates on key terms and whether the detector's mic cluster widens.🤖 Generated with Claude Code